Method, system, and computer program product for avoiding data loss during network port recovery processes

ABSTRACT

A method, system, and computer program product are disclosed in a data processing system for avoiding data loss during network port recovery. A first network port is linked to a second network port via a network. The second network port transmits data to the first network port via the network. A determination is made that the first network port needs to be reinitialized. Prior to the first network port executing a re-initialization process, the first network port notifies the second network port to pause its data transmissions to the first network port.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention is directed to data processing systems. Morespecifically, the present invention is directed to a method, system, andcomputer program product for avoiding data loss during a network port'srecovery process.

2. Description of Related Art

In an ideal data processing system networking environment, the networkports, also called adapters, are operational at all times once they havebeen initialized and have addresses resolved. However, the reality isthat often times a small number of ports experience some kind of portfailure while in operation due to hardware or software defects. Thesefailures may cause the port to hang, i.e. the port will not respond, insome cases. Once a port hangs, the port needs to complete a recoveryprocess before it can become active and responsive again.

The known method to recover a port is to issue a soft reset to the portwhich will then cause the port to reinitialize itself. The process ofreinitializing the port takes some period of time. During this timeperiod of re-initialization, the port software and hardware are notready or available to receive any packets from the network. Any packetssent to the port during this reinitialization process will be lost. Tocompound this problem, the system that transmitted the lost data to theport will be unaware that the intended recipient port is in a recoverymode and is not receiving the data.

A data processing system may be linked to another data processing systemvia the network in order to transmit data between these linked systemsutilizing a network port in each system. When a first data processingsystem is linked to a second data processing system, the first dataprocessing system will assume that because the systems are linked thatthe second system is ready to receive data via the second system'snetwork port.

An Ethernet port includes a media access controller (MAC) and a networkphysical (PHY) layer. The logic to establish an Ethernet link connectionbetween the ports is in the physical layer of the Ethernet port and isindependent from the MAC and the device driver software that executes arecovery of the port. As soon as a port receives a power on signal or asoft reset signal, the PHY will start link negotiations with a seconddata processing system that is to become its linked partner. The linkcan be accomplished very quickly and long before the port software(device driver) and hardware (MAC) are ready to receive any data via theport. During the recovery period, there can be a significant data lossif the data keeps coming from the linked data processing system into thefailed port.

Therefore, a need exists for a method, system, and computer programproduct for avoiding data loss during a network port recovery process.

SUMMARY OF THE INVENTION

A method, system, and computer program product are disclosed in a dataprocessing system for avoiding data loss during a network port'srecovery process. A first network port is linked to a second networkport via a network. The second network port transmits data to the firstnetwork port via the network. A determination is made that the firstnetwork port needs to be reinitialized. Prior to the first network portexecuting a re-initialization process, the first network port notifiesthe second network port to pause its data transmissions to the firstnetwork port. The first network port may then complete its recoveryprocess which includes reinitializing the first port. During the firstport's recovery process, the second port will not send data to the firstport. Once the first port has completed its recovery process, the firstport will notify the second port that it may again send data to thefirst port.

The above as well as additional objectives, features, and advantages ofthe present invention will become apparent in the following detailedwritten description.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed characteristic of the invention are setforth in the appended claims. The invention itself, however, as well asa preferred mode of use, further objectives and advantages thereof, willbest be understood by reference to the following detailed description ofan illustrative embodiment when read in conjunction with theaccompanying drawings, wherein:

FIG. 1 is a pictorial representation which depicts a network of dataprocessing systems in accordance with the present invention;

FIG. 2 is a more detailed illustration of a computer system that may beused to implement any of the computer systems of FIG. 1 in accordancewith the present invention;

FIG. 3 illustrates a high level flow chart that depicts a first networkport transmitting a pause frame to a second network port before enteringa recovery mode, where the pause frame causes the second network portthat is linked to the first network port to pause its data transmissionsto the first network port in accordance with the present invention; and

FIG. 4 depicts a high level flow chart that illustrates a first networkport executing a recovery exit process in accordance with the presentinvention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

A preferred embodiment of the present invention and its advantages arebetter understood by referring to the figures, like numerals being usedfor like and corresponding parts of the accompanying figures.

To avoid any loss of data that is destined to a network port that is ina recovery mode, the present invention provides for sending a packet tothe network port that is linked to the port in recovery. This packet ispreferably an IEEE 802.3x flow control standard packet. A packet thatconforms to this standard includes a settable timer value. When a portreceives a packet that conforms to this standard, the port that receivesthe packet will pause its data transmissions to the port that sent thepacket until the timer value included in the pause frame expires.

The present invention provides a method, system, and computer programproduct that detects a first network port entering a recovery modeprocess. This first network port is linked to a second network port viaan Ethernet link standard process. After the first network port hasentered a recovery mode process, but prior to beginning are-initialization of the port, the first port will transmit a packetthat conforms to the IEEE 802.3x flow control standard to the secondport. Thus, the second port will pause its data transmissions to thefirst port until the timer value set by the packet has expired.

Once the first port sends its first pause packet, the first port willstart its re-initialize process to re-initialize the first port. Thefirst port will continue to send pause packets that conform to this802.3x flow control standard until the first port has completed itsrecovery process and is reinitialized. When the first port has completedits recovery mode process and is reinitialized, the first port will thensend another pause packet to the second port. This second packet has atimer set to a second value. This second value is preferably zero. Whenthe second port receives this packet, it will pause for zero secondsbefore resuming its data transmissions to the first port. Thus, when thesecond port receives this second packet, it will resume transmittingdata to the first port which is now again ready to receive the dataafter being reinitialized.

FIG. 1 depicts a pictorial representation of a network of dataprocessing systems in which the present invention may be implemented.Network data processing system 100 is a network of computers in whichthe present invention may be implemented. Network data processing system100 contains a network 102, which is the medium used to providecommunications links between various devices and computers connectedtogether within network data processing system 100. Network 102 mayinclude connections, such as wire, wireless communication links, orfiber optic cables.

In the depicted example, a server 104 is connected to network 102 alongwith storage unit 106. In addition, clients 108, 110, and 112 also areconnected to network 102. These clients 108, 110, and 112 may be, forexample, personal computers, network computers, or other computingdevices. In the depicted example, server 104 provides data, such as bootfiles, operating system images, and applications to clients 108-112.Clients 108, 110, and 112 are clients to server 104. Network dataprocessing system 100 may include additional servers, clients, and otherdevices not shown. In the depicted example, network data processingsystem 100 is the Internet with network 102 representing a worldwidecollection of networks and gateways that use the TCP/IP suite ofprotocols to communicate with one another. At the heart of the Internetis a backbone of high-speed data communication lines between major nodesor host computers, consisting of thousands of commercial, government,educational and other computer systems that route data and messages.

Of course, network data processing system 100 also may be implemented asa number of different types of networks, such as for example, anintranet, a local area network (LAN), a wide area network (WAN), or awireless network. FIG. 1 is intended as an example, and not as anarchitectural limitation for the present invention.

As described in more detail below, one of these computer systems, suchas client 108 may be linked to another computer system, such as client110. Thus, client 108 will include a network adapter or port that islinked to a network adapter that is included in client 110. These twoclients 108, 110 are thus linked via network 102. Preferably, network102 is an Ethernet network and the clients are linked via an Ethernetstandard link.

In addition, each adapter includes recovery logic that includes flagsthat are used to indicate whether the adapter is currently ready toreceive data transmissions from its linked network adapter that residesin the linked client. In addition, the adapter includes another flagthat indicates whether a recovery process has been completed by thenetwork adapter. Thus, a first network adapter uses these flags todetermine whether to indicate to a second adapter that is linked to thefirst adapter to pause transmissions of data from the second adapter tothe first adapter.

FIG. 2 is a more detailed illustration of a computer system that may beused to implement any of the computer systems of FIG. 1 in accordancewith the present invention. Data processing system 200 may be asymmetric multiprocessor (SMP) system including a plurality ofprocessors 202 and 204 connected to system bus 206. Alternatively, asingle processor system may be employed. In the depicted example,processor 204 is a service processor. Also connected to system bus 206is memory controller/cache 208, which provides an interface to localmemory 209. I/O bus bridge 210 is connected to system bus 206 andprovides an interface to I/O bus 212. Memory controller/cache 208 andI/O bus bridge 210 may be integrated as depicted.

Peripheral component interconnect (PCI) bus bridge 214 connected to I/Obus 212 provides an interface to PCI local bus 216. A number of modemsmay be connected to PCI bus 216. Typical PCI bus implementations willsupport four PCI expansion slots or add-in connectors. Communicationslinks to network computers 108-112 in FIG. 1 may be provided throughmodem 218 and network adapter 220 connected to PCI local bus 216 throughadd-in boards.

Network adapter 220 includes a physical layer 282 which conditionsanalog signals to go out to the network, such as for example an Ethernetnetwork over an R45 connector. A media access controller (MAC) 280 isincluded within network adapter 220. Media access controller (MAC) 280is coupled to bus 216 and processes digital network signals. MAC 280serves as an interface between bus 216 and physical layer 282. MAC 280performs a number of functions involved in the transmission andreception of data packets. For example, during the transmission of data,MAC 280 assembles the data to be transmitted into a packet with addressand error detection fields. Conversely, during the reception of apacket, MAC 280 disassembles the packet and performs address checkingand error detection. In addition, MAC 280 typically performsencoding/decoding of digital signals transmitted and performs preamblegeneration/removal as well as bit transmission/reception.

Network adapter 220, also called network port, includes recovery logic283. The recovery reset flag and receive ready flag described in moredetail below may be either hardware flags, software flags, or acombination of both. If these flags are implemented in hardware, theywill be included within recovery logic 283.

Additional PCI bus bridges 222 and 224 provide interfaces for additionalPCI buses 226 and 228, from which additional modems or network adaptersmay be supported. In this manner, data processing system 200 allowsconnections to multiple network computers. A memory-mapped graphicsadapter 230 and hard disk 232 may also be connected to I/O bus 212 asdepicted, either directly or indirectly.

Service processor 204 interrogates system processors, memory components,and I/O bridges to generate an inventory and topology understanding ofdata processing system 200. Service processor 204 also executesBuilt-In-Self-Tests (BISTs), Basic Assurance Tests (BATs), and memorytests on all elements found by interrogating a system processor, memorycontroller, and I/O bridge. Any error information for failures detectedduring the BISTs, BATs, and memory tests are gathered and reported byservice processor 204.

Those of ordinary skill in the art will appreciate that the hardwaredepicted in FIG. 2 may vary. For example, other peripheral devices, suchas optical disk drives and the like, also may be used in addition to orin place of the hardware depicted. The depicted example is not meant toimply architectural limitations with respect to the present invention.

The present invention may be executed by one of the computers depictedby FIG. 1 or 2.

FIG. 3 illustrates a high level flow chart that depicts a first networkport transmitting a pause frame before entering a recovery mode, wherethe pause frame causes a second network port that is linked to the firstnetwork port to pause its data transmissions to the first network portin accordance with the present invention. The process starts as depictedby block 300 and thereafter passes to block 302 which illustrates anetwork port, also called a network adapter, such as network adapter220, receiving a recovery signal, such as a soft reset.

The process then passes to block 304 which depicts the port entering therecovery mode. Next, block 306 illustrates setting a recovery reset flagequal to “yes”. Thereafter, block 308 depicts setting a receive readyflag equal to “no”. Block 310, then, illustrates the port sending anXoff frame to the data processing system that includes the network portthat is currently linked to the network port that sent this frame. ThisXoff frame is a packet that adheres to the 802.3x flow control standardand includes a first timer value set to a first value. The first valueis preferably a maximum value.

Next, block 312 depicts a determination of whether or not the recoveryreset flag is equal to “yes” or to “no”. If a determination is made thatthe recovery reset flag is currently set to “no”, the process passes toblock 318. Referring again to block 312, if a determination is made thatthe recovery reset flag is currently set to “yes”, the process passes toblock 314 which illustrates the recovery logic executing the normalrecovery process which initializes the port.

The process then passes to block 316 which depicts setting the recoveryreset flag equal to “no”. Next, block 318 illustrates a determination ofwhether or not the time in the Xoff frame has expired. This is referredto as the Xoff timer being “timed out”. If a determination is made thatthe Xoff frame has not timed out, i.e. there is still time remaining inthe timer value, the process passes back to block 318. Referring againto block 318, if a determination is made that the Xoff frame has timedout, the process passes to block 320.

Block 320 depicts a determination of whether or not the receive readyflag value is currently “yes” or “no”. If a determination is made thatthe receive ready flag is set to “no”, the process passes back to block310. Thus, another Xoff frame having a timer set to a maximum value willbe sent to the linked port. This loop will continue sending out multipleXoff frames until the receive ready flag is set to “yes”. Referringagain to block 320, if a determination is made that the receive readyflag is current set to “yes”, the process terminates as illustrated byblock 322.

FIG. 4 depicts a high level flow chart that illustrates a first networkport executing a recovery exit process in accordance with the presentinvention. The process starts as depicted by block 400 and thereafterpasses to block 402 which illustrates the recovery completion logicmonitoring recovery process status by continually monitoring therecovery reset flag. When the recovery process is complete, the recoveryreset flag will be set to “no”.

Next, block 404 depicts a determination of whether or not the recoveryprocess is complete. If a determination is made that the recoveryprocess is not complete, i.e. the recovery reset flag is equal to “yes”,the process passes back to block 404 until which time as the recoveryreset flag becomes equal to “no”. Referring again to block 404, if adetermination is made that the recovery process is complete, i.e. therecovery reset flag is equal to “no”, the process passes to block 406which illustrates entering the recovery exit mode. Thereafter, block 408depicts setting the receive ready flag equal to “yes”. Block 410, then,illustrates sending an Xon frame to the linked port with a timer valueset to a second value. This second value is preferably zero. Thereafter,block 412 depicts a completion of the recovery exit mode. The processthen terminates as illustrated by block 414.

It is important to note that while the present invention has beendescribed in the context of a fully functioning data processing system.Those of ordinary skill in the art will appreciate that the processes ofthe present invention are capable of being distributed in the form of acomputer readable medium of instructions and a variety of forms and thatthe present invention applies equally regardless of the particular typeof signal bearing media actually used to carry out the distribution.Examples of computer readable media include recordable-type media, suchas a floppy disk, a hard disk drive, a RAM, CD-ROMs, DVD-ROMs, andtransmission-type media, such as digital and analog communicationslinks, wired or wireless communications links using transmission forms,such as, for example, radio frequency and light wave transmissions. Thecomputer readable media may take the form of coded formats that aredecoded for actual use in a particular data processing system.

The description of the present invention has been presented for purposesof illustration and description, and is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the art. Theembodiment was chosen and described in order to best explain theprinciples of the invention, the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

1.-9. (canceled)
 10. A data processing system for avoiding data lossduring network port recovery, said system comprising: a first networkport linked to a second network port via a network, said second networkport transmitting data to said first network port via said network; saidfirst network port receiving a reinitialized signal; and prior to saidfirst network port executing a re-initialization process, said firstnetwork port notifying said second network port to pause its datatransmissions to said first network port.
 11. The system according toclaim 10, further comprising: said second network port pausing datatransmissions to said first network port in response to being notified.12. The system according to claim 10, further comprising: said secondnetwork port pausing data transmissions to said first network port; saidfirst network port determining that said first network port hascompleted its re-initialization process; and said first network portnotifying said second network port to resume its data transmissions tosaid first network port.
 13. The system according to claim 10, furthercomprising: said first network port executing a re-initializationprocess while said second network port pauses its data transmissions tosaid first network port.
 14. The system according to claim 10, furthercomprising: said first network port providing a timer value to saidsecond network port prior to said first network port beginning itsre-initialization process; and said second network port pausing datatransmissions to said first network port until said timer value expires.15. The system according claim 14, further comprising: said firstnetwork port determining that said timer value has expired; in responseto determining that said timer value has expired, said first networkport determining whether it has completed its re-initialization process;in response to a determination that said first network port has notcompleted its re-initialization process, said first network portproviding a second timer value to said second network port; and saidsecond network port pausing data transmissions to said first networkport until said second timer value expires.
 16. The system according toclaim 14, further comprising: said first network port determining thatsaid timer value has expired; in response to determining that said timervalue has expired, said first network port determining whether it hascompleted its re-initialization process; in response to a determinationthat said first network port has completed its re-initializationprocess, said first network port providing a third timer value to saidsecond network port; and said second network port resuming datatransmissions to said first network port upon a receipt of said thirdtimer value.
 17. The system according to claim 16, further comprising:said third timer value being a value of zero.
 18. The system accordingto claim 10, further comprising: a first flag for determining whethersaid first network port has begun its re-initialization process.
 19. Acomputer program product for avoiding data loss during network portrecovery, said product comprising: instruction means for linking a firstnetwork port to a second network port via a network, said second networkport transmitting data to said first network port via said network;instruction means for determining that said first network port needs tobe reinitialized; prior to said first network port executing are-initialization process, instruction means for notifying, by saidfirst network port, said second network port to pause its datatransmissions to said first network port; and pausing, by said secondnetwork port, data transmissions to said first network port.
 20. Theproduct according to claim 19, further comprising: instruction means forpausing, by said second network port, data transmissions to said firstnetwork port; instruction means for determining that said first networkport has completed its re-initialization process; and instruction meansfor notifying, by said first network port, said second network port toresume its data transmissions to said first network port.